When you update the password using SAS Deployment Manager in SAS 9.4M5 , the Sockets Layer (SSL) configuration settings for SAS Web Server are not preserved.

This problem occurs when you perform these steps:

1. Deploy a SAS^® middle tier with SAS Web Server that is configured for SSL and the HTTPS protocol.
2. Update the SAS Web Server with new certificates (for example, you switch the certificates from self-signed to signed, or you renew them).
3. Update a managed password account (for example, sasadm@saspw) in SAS Deployment Manager.

Upon following these steps, the SSL folder for SAS Web Server (SAS-configuration-directory/LevN/Web/WebServer/ssl) is backed up to a new folder and a new ssl folder is created. This new folder contains the certificates that were used during initial deployment. As a result, SAS Web Server fails to start. In addition, if SAS Deployment Manager cannot find the certificates that were used in the initial deployment, then deployment manager fails.

In either scenario, the SAS Web Server ssl folder is deleted.

For a workaround to this issue, contact SAS Technical Support.

Note: This problem is fixed in SAS 9.4M6. The following changes have been made in the 9.46M release:

• A new certificate is installed in SAS-configuration-directory/LevN/Web/WebServer/ssl/*.crt.
• A new private key is installed in SAS-configuration-directory//LevN/Web/WebServer/ssl/*.key.

However, be aware that the Summary section of UpdatePasswords*.html file (in SAS-configuration-directory/ /LevN/Documents/) still states (incorrectly) that a new key and certificate were installed into the SAS Web Server ssl directory. 

Operating System and Release Information